Assessing the Unseen: Roles of Confidentiality and Trust in Software Engineering Work-based Learning Programmes [Poster]

A typical academic degree focused on software engineering has little practical relationship with the industry it is named for, other than the occasional placement or internship. Unlike other professions such as medicine, dentistry and veterinary sciences, candidates do not need to participate in significant professional practice to earn their degree. Indeed, if we consider a traditional academic software engineering student they probably have far more experience constructing shiny new ‘green-field’ systems, than maintaining the old ‘brown-field’ systems found in industry, and generating most professional work. Consequently, there is growing enthusiasm for work-based learning programmes that provide an opportunity for candidates to cement abstract academic theory in concrete personal experience. Work-based learning software engineering students earn their degree by combining theory with actual practice in a professional environment. Nevertheless, the intangible outcomes for much of software engineering has led to an industry obsessed with confidentiality, driven by concerns of employees smuggling source code to competitors or regulators. This obsession potentially presents a barrier to work-based learning schemes as employers prevent outsiders, even close higher education partners, from observing the systems and the source code that learners are working on. Learners may have the opportunity for concrete personal experience, but educators are barred from observing any such experience. However, confidentiality agreements may not necessarily present barriers to assessment, but instead provide an opportunity to assess comprehension and transferable skills by requiring abstract descriptions and reports. This is the converse to the problem in some programming courses, where students submit code without demonstrating that they understand it and can discuss it in terms of the concepts taught. In this talk and accompanying poster we explore some models for software engineering work-based learning programmes that have the potential to maintain confidentiality while assessing learners’ comprehension and ability. We invite discussion and criticism from conference attendees of the presented models, and are interested in potential partners for future collaboration

An evaluation of a professional learning network for computer science teachers

This paper describes and evaluates aspects of a professional development programme for existing CS teachers in secondary schools (PLAN C) which was designed to support teachers at a time of substantial curricular change. The paper’s particular focus is on the formation of a teacher professional development network across several hundred teachers and a wide geographical area. Evidence from a series of observations and teacher surveys over a two-year period is analysed with respect to the project’s programme theory in order to illustrate not only whether it worked as intended, by why. Results indicate that the PLAN C design has been successful in increasing teachers’ professional confidence and appears to have catalysed powerful change in attitudes to learning. Presentation of challenging pedagogical content knowledge and conceptual frameworks, high-quality teacher-led professional dialogue, along with the space for reflection and classroom trials, triggered examination of the teachers’ own current practices

The Effect of a Spatial Skills Training Course in Introductory Computing

Spatial skills have been associated with STEM success for decades. Research has shown that training spatial skills can have a positive impact on outcomes in STEM domains such as engineering, mathematics and physics; however -- despite some promising leads -- evidence for the same relationship with computing is limited. This research describes a spatial skills intervention delivered to around 60 students in introductory computing courses who tested with relatively low spatial skills, mirroring a well established intervention developed and used by Sorby in engineering for over 20 years. This study has shown correlation between spatial skills and computing assessment marks which was observed both before and after training took place, suggesting that as the students' spatial skills are improved via training, so too is their computing assessment. Students who took part in the intervention also showed a significant increase in class rankings over their peers. The authors consider this to be a good indication that spatial skills training for low spatial skills scorers starting a computing degree is of value

Flexible Low-cost Activities to Develop Novice Code Comprehension Skills in Schools

The lack of code comprehension skills in novice programming students is recognised as a major factor underpinning poor learning outcomes. We use Schulte’s Block Model to support teachers’ understanding of how to break the skill down into component parts that are more manageable for a learner. This analysis is operationalised in three code annotation-based learning/assessment exercise formats, two helping students to identify and describe programming concepts and the third enabling them to parse code correctly and carry out desk executions. A great benefit of the activities is that they are low cost and can be applied to any imperative style code and so can be easily adopted by schools anywhere; furthermore, they are active, not passive, an issue with some animation-based visualisation approaches. The exercise formats were included as part of a national schools computing science professional learning programme (PLAN C)

The abstraction transition taxonomy: developing desired learning outcomes through the lens of situated cognition

We report on a post-hoc analysis of introductory programming lecture materials. The purpose of this analysis is to identify what knowledge and skills we are asking students to acquire, as situated in the activity, tools, and culture of what programmers do and how they think. The specific materials analyzed are the 133 Peer Instruction questions used in lecture to support cognitive apprenticeship -- honoring the situated nature of knowledge. We propose an Abstraction Transition Taxonomy for classifying the kinds of knowing and practices we engage students in as we seek to apprentice them into the programming world. We find students are asked to answer questions expressed using three levels of abstraction: English, CS Speak, and Code. Moreover, many questions involve asking students to transition between levels of abstraction within the context of a computational problem. Finally, by applying our taxonomy in classifying a range of introductory programming exams, we find that summative assessments (including our own) tend to emphasize a small range of the skills fostered in students during the formative/apprenticeship phase

Demystifying and Decluttering Participation in Software Engineering Education Programmes

Academics and employers can partner to deliver professional software engineering education via work-based learning (WBL) programmes. These programmes have the potential to engage and motivate under-represented groups, including those that would not normally engage in higher education. However, challenges still exist in supporting such individuals in participating in WBL programmes. Consequently, we discuss a project on broadening participation in WBL software engineering to support individuals from under-represented groups to participate in software engineering education

What Do We Do When We Teach Software Engineering?

Many UK higher education institutions offer software engineering programmes, but the purpose and relevance of these programmes within computing science departments is not always obvious. The reality is that while advanced economies require many more skilled software engineers, universities are not delivering them. This is at least true in the context of the United Kingdom, where there are high numbers of software engineering vacancies and unemployed software engineering graduates. A possible explanation could be that curriculum content of software engineering programmes in universities needs to be reconsidered to meet the needs of industry. However, reconsidering curriculum content alone is unlikely to be transformative as there is little to be gained from changing to an emerging methodology, language or framework. Instead, an alternative direction could be to reconsider curriculum delivery and the identity of software engineering within computing science itself. In this paper, we contextualise the challenge by considering the history of software engineering education and some of its key developments. We then consider some of the alternative delivery approaches, before arguing cooperative programmes provide a opportunity for institutions to reconsider software engineering education

Relating Spatial Skills and Expression Evaluation

Work connecting spatial skills to computing has used course grades or marks, or general programming tests as the measure of computing ability. In order to map the relationship between spatial skills and computing more precisely, this paper picks out a particular subset of possible programming concepts and skills, that of expression evaluation. The paper describes the development of an expression evaluation test, which aims to identify participants' ability to perform evaluations of expressions across a range of complexity. The results indicate participants' expression evaluation ability was significantly correlated with a spatial skills test (r=0.48), even more so when only considering those with less prior programming experience (r=0.58). Thus, we have determined that spatial skills are of value in expression evaluation exercises, particularly for beginners

Enthusing and inspiring with reusable kinaesthetic activities

We describe the experiences of three University projects that use a style of physical, non-computer based activity to enthuse and teach school students computer science concepts. We show that this kind of activity is effective as an outreach and teaching resource even when reused across different age/ability ranges, in lecture and workshop formats and for delivery by different people. We introduce the concept of a Reusable Outreach Object (ROO) that extends Reusable Learning Objects. and argue for a community effort in developing a repository of such objects

Code or (Not Code): Separating Formal and Natural Language in CS Education

This paper argues that the "institutionalised understanding" of pseudo-code as a blend of formal and natural languages makes it an unsuitable choice for national assessment where the intention is to test program comprehension skills. It permits question-setters to inadvertently introduce a level of ambiguity and consequent confusion. This is not in keeping with either good assessment practice or an argument developed in the paper that CS education should be clearly fostering the skills needed for understanding formal, as distinct from natural, languages. The argument is backed up by an analysis of 49 questions drawn from the national school CS examinations of a single country, spanning a period of six years and two phases -- the first in which no formal pseudo-code was defined, the second in which a formal reference language, referred to as a "formally-defined pseudo-code", was provided for teachers and exam setters. The analysis demonstrates that in both phases, incorrect, confusing or ambiguous code was presented in questions. The paper concludes by recommending that the term reference language should be used in place of pseudo-code, and an appropriate formally-defined language specified, in national exam settings where a common language of assessment is required. This change of terms emphasises the characteristics required of a language to be used for assessment of program comprehension. The reference language used in the study is outlined. It was designed by the authors for human readability and also to make absolutely explicit the demarcation between formal and informal language, in such a way that automated checking can be carried out on programs written in the language. Formal specifications and a checker for the language are available